Multi-Path Replication in Databases

ABSTRACT

Systems, methods and computer program products for multi-path replication in databases are described herein. A non-limiting embodiment includes instantiating a plurality of replicate connections to a replicate database, providing transactions to the replicate database through a plurality of transaction streams, where the transaction streams associated with respective instantiated replicate connections. Transactions occurring in distinct transaction streams are applied, in parallel, at the replicate database. Another non-limiting embodiment includes instantiating a plurality of replication sender threads, where the replication sender threads communicate in parallel with respective replication servers over respective replication paths. Data sharing one or more attributes can be bound to a replication path in communication with the respective replication servers.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of co-pending U.S. patent applicationSer. No. 13/618,785, filed on Sep. 14, 2012, and claims benefit to U.S.Provisional Patent Application No. 61/559,845, filed on Nov. 15, 2011,the entire contents of which are hereby incorporated by reference.

BACKGROUND

1. Field

Embodiments of the present invention generally relate to databasesystems, and particularly to database replication using multiplereplication paths.

2. Background Discussion

Data replication is the process of maintaining multiple copies of adatabase object in a distributed database system. Performanceimprovements can be achieved when data replication is employed, sincemultiple access locations exist for the access and modification of thereplicated data. For example, if multiple copies of a data object aremaintained, an application can access the logically “closest” copy ofthe data object to improve access times and minimize network traffic. Inaddition, data replication provides greater fault tolerance in the eventof a server failure, since the multiple copies of the data objecteffectively become online backup copies if a failure occurs.

Conventional replication architecture supports a single path (or stream)of data between a primary (or source) database and a replication server.Specifically, database transactions are replicated at a target (orreplicate) database, serially, in a single replication path, to maintaina transaction commit order at the primary database.

In some instances, however, this replication architecture can provedisadvantageous. For instance, when throughput activity at the primarydatabase is high, the replication server (responsible for replicatingtransactions at the target database) cannot maintain the low replicationlatency expected by users at the target database. In other words, timetaken to replicate database operations increases significantly as alarge number of operations begin to be committed at the primarydatabase.

Thus, as replicated transaction and data volume increases, traditionalreplication solutions utilizing a single replication path cannot matchdata generation/transaction speeds at the primary database. This causesboth data accumulation and significant transaction latency.

In addition, transactions applied at the primary database can havedifferent replication priorities. Some transactions are expected to bereplicated sooner than other transactions at the target database.However, conventional replication techniques are limited to seriallyreplicating transactions in an order that the transactions werecommitted in at the primary database. Accordingly, systems and methodfor replicating data that maintain low replication latency duringperiods of high throughput activity at the primary database and thathave the ability to prioritize transactions are needed.

BRIEF SUMMARY

Briefly stated, embodiments of the invention include system, method,computer program product embodiments, and combinations andsub-combinations thereof, for multi-path database replication.

A non-limiting embodiment includes instantiating a plurality ofreplicate connections to a replicate database, providing transactions tothe replicate database through a plurality of transaction streams, wherethe transaction streams are associated with respective instantiatedreplicate connections. Transactions occurring in distinct transactionstreams can be applied, in parallel, at the replicate database.

The embodiment further includes instantiating a plurality of connectionsto replication agent threads associated with a primary database andselectively assigning a replication path to a transaction based on thetransaction's replication priority. The embodiment further includesidentifying a path with less transaction congestion compared totransaction congestion in other replication paths and assigning areplication transaction with high replication priority to the identifiedpath.

Another non-limiting embodiment includes instantiating a plurality ofreplication sender threads, where the replication sender threadscommunicate in parallel with respective replication servers overrespective replication paths. Data sharing one or more attributes isbound to a distinct replication path in communication with therespective replication servers.

In this way, embodiments improve replication performance and quality ofservice, regardless of replicated transaction volume at a primarydatabase, by resolving transactions into a plurality of transactionstreams. The transactions can be applied at a replicate database inparallel or in any order of transaction priority.

Furthermore, embodiments can bind database objects to replicationchannels, so that a replication server in control of a channel canreceive data bound to the channel. In other words, data can be filteredfrom other data by binding the data to a channel assigned to areplication server before it is delivered to the replication server. Inthis way, replication transaction load can be distributed across aplurality of replication servers so that each replication server canprovide improved replication performance.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and form partof the specification, illustrate embodiments of the present inventionand, together with the description, further serve to explain theprinciples of the invention and to enable a person skilled in therelevant art(s) to make and use the invention.

FIG. 1 is a diagram of an example replication environment.

FIG. 2A is a diagram of a multi-path replication environment, accordingto an embodiment.

FIG. 2B is a diagram of a multi-path replication environment, accordingto another embodiment.

FIG. 3 illustrates a conventional replication environment.

FIG. 4 illustrates a multi-path replication environment enabling bindingof objects to replication channels, according to an embodiment.

FIG. 5 illustrates an example computer useful for implementingcomponents of the embodiments.

FIG. 6 is a flowchart illustrating a method of replicating dataaccording to embodiments of the invention.

FIG. 7 is a flowchart illustrating a method of replicating dataaccording to embodiments of the invention.

The features and advantages of the present invention will become moreapparent from the detailed description set forth below when taken inconjunction with the drawings. In the drawings, like reference numbersgenerally indicate identical, functionally similar, and/or structurallysimilar elements. Generally, the drawing in which an element firstappears is indicated by the leftmost digit(s) in the correspondingreference number.

DETAILED DESCRIPTION

Embodiments of the present invention relate to systems, methods andcomputer program products for multi-path replication.

While embodiments of the present invention are described herein withreference to illustrative embodiments for particular applications, itshould be understood that the invention is not limited thereto. Thoseskilled in the art with access to the teachings provided herein willrecognize additional modifications, applications, and embodiments withinthe scope thereof and additional fields in which the invention would beof significant utility.

As used herein, the term “commit order” (or transaction serialization)refers to an order of transactions applied at a primary database. Asnoted above, conventional replication approaches maintain a commit orderof transactions that occur at the primary database.

As used herein, the term “transaction integrity” refers to a set of rowmodifications captured at a primary database for replication inaccordance with business (or replication) rules. For example, notintended to be limiting, transaction integrity may be violated ifdifferent row modifications to different tables within transactions weredelivered by different replicate connections.

As used herein, the term “parallelizable transactions” refers totransactions that may be replicated without regard to a primarytransaction commit serialization order, and yet maintain databaseconsistency when the transactions are applied according toparallelization rules.

As used herein, the term “parallelization rules” refers to transactionattributes or data values that can be used to segregate parallelizabletransactions. Examples of transaction attributes include, but are notlimited to, an origin session ID, an origin user, a set of origintables, an origin transaction name, etc.

With reference to the term “replication priority,” and as a non-limitingexample, if transaction A is expected to be replicated at a replicatedatabase with a smaller latency than another transaction B, transactionA can be considered to have a higher replication priority thantransaction B. Also for example, transactions A & B can beparallelizable transactions to maintain database consistency.

As used herein, the term “primary connection” refers to instances ofcomponents including, but not limited to, an executor (EXEC) module,inbound queue and distributor module. As a non-limiting example, areplication server may set up a primary connection for eachprimary/active database. Also, for example, a primary connection namemay be identical to a database name.

As used herein, the term “replicate connection” refers to instances ofcomponents including, but not limited to, an outbound queue, adata-server interface (DSI) scheduler thread and a DSI execute thread.As an example, a replication server may instantiate a replicateconnection for each replicate database and also instantiate a replicateconnection without an outbound queue for a standby database. Also, forexample, a replicate connection name may be identical to areplicate/standby database name.

As used herein, the term “replication path” references transactions froma primary database that are replicated to a replicate database throughcomponents of a replication system. These components may include, butare not limited to, a replication agent module or thread, an EXECmodule, an inbound queue, a distributor (DIST) module, route, outboundqueue and a DSI module. In a standby environment, transactions from anactive database are replicated to the standby database throughcomponents including, but are not limited to, a replication agentmodule, an EXEC module, an inbound queue and a DSI module. As anon-limiting example, a set of replication instances including suchcomponents can be considered to be a replication path.

Furthermore, a “path” can be considered to be an example of a namedchannel over which data is transported from a database to a replicationserver. In a non-limiting embodiment, a replication agent thread canresolve a “path” into at least two parts, i.e., a logical path and aphysical path (discussed below).

As used herein, the term replication server (“RS”) definition includes,but is not limited to, connectivity and configuration information toconnect a replication agent thread (RAT) sender to a given replicationserver.

As used herein, the term “scanner” refers to a task that can beresponsible for reading a transaction log for records for replication,and routing these records to an appropriate sender (e.g., RAT sender).

As used herein, the term “sender” refers to a thread (that can becontrolled by the scanner) that can connect to a specified replicationserver to exchange replication data.

As used herein, a “bind” operation can be used to create an associationbetween a database object and a “path.”

As used herein, a “physical path” defines a replication server that isto receive data bound to the path along with one or more characteristicsof the path. In a non-limiting embodiment, a “physical path”encapsulates how senders are to connect to a replication server. Aphysical path can also hold a RS definition and additional multi-pathreplication information.

As used herein, “logical paths” can be used to group one or morephysical paths under a single name to facilitate association ofreplicate data when the replicate data is to be distributed to multipletargets. For example, a dimension table may need to be replicated to allavailable destinations in a replication environment. Instead ofrequiring users to bind each dimension table to each respectivedestination, a single operation may be needed for each replicatedobject, according to a non-limiting example.

In general, and as a non-limiting example, a logical path represents a1:N relationship with available physical paths where N=1−(a number ofphysical paths). In a non-limiting embodiment, a logical path createdwhen a physical path is initially defined is closely coupled to anunderlying physical path and thus can allow users a handle to modifyassociated configuration, if necessary. Other logical paths areconsidered “strict,” and are loosely coupled to an underlying physicalpath and can be used to give users a convenient means of routing data tosets of destinations. In an embodiment, logical paths, strict orotherwise, are targets to which database objects can be bound.

As used herein, “DSI” refers to a dataserver interface thread. As anon-limiting example, a DSI reads transactions from a queue and appliesthe transactions to a replicate database.

As used herein, “DIST” refers to a distributor thread. As a non-limitingexample, each primary connection can have a DIST thread. A DIST maydetermine a replicate database to which transactions from the primarydatabase are to be distributed in accordance with replicationdefinitions and subscriptions defined in a replication server.

As used herein, “EXEC” refers to an executor thread. An executor threadcan handle incoming connections from a replication agent and placetransactions sent by the replication agent into stable queues.

The example definitions discussed above are purely illustrative and arenot intended to limit the embodiments.

This section describes an exemplary replication environment, accordingto an embodiment of the invention illustrated in FIG. 1.

FIG. 1 includes primary database 110, replication agent 140, replicationserver 130, replicate databases 120 a-120N and network 102. Theinvention is applicable to any system having generally the structure ofFIG. 1, or that would benefit from the operation, methods and functionsas described herein. FIG. 1 is purely illustrative and is not intendedto limit the invention.

Primary database 110 may be any form of database and can include, but isnot limited to, a device having one or more processors and memory forexecuting and storing instructions. Such a database may includesoftware, firmware, and hardware or some combination thereof. Thesoftware may include one or more applications and an operating system.The hardware can include, but is not limited to, a processor, memory anduser interface display. An optional input device, such as a mouse,stylus or any other pointing device, may be used.

In an embodiment, primary database 110 is a source of transactions thatmanipulate and/or modify data in replicate databases 120 _(a)-120 _(N).Tables marked for replication in a primary database 110 may be known asmarked tables (not shown). In an embodiment, a primary table is markedfor replication (e.g., marked by a database administrator) so thatreplication agent 140 can identify and replicate transactions thataffect the data in the table using replication server 130.

Replication agent 140 can capture replicated transactions (i.e.,transactions occurring on marked tables) in primary database 110, andthen may send those transactions to replication server 130 fordistribution to replicate databases 120 _(a)-120 _(N). In an embodiment,replication agent 140 provides a transaction log of one or moretransactions at primary database 110 to replication server 130. In anembodiment, replication agent 140 instantiates one or more replicationagent threads in primary database 110 or any other components of system100. A replication agent thread, according to an embodiment, isdiscussed further below.

In an embodiment, replication agent 140 runs as a stand-aloneapplication, independent of primary database 110, replication server130, and any other replication system component. In another embodiment,replication agent 140 may reside on the same host machine as, forexample, primary database 110 or any other replication system component.

Replication server 130 can receive, from replication agent 140,transactions that are to be replicated at replicate databases 120_(a)-120 _(N). In an embodiment, replication server 130 may sendreplicated transactions to replicate databases 120 _(a)-120 _(N) inresponse to one or more commands from replication agent 140. In anembodiment, replicate databases 120 _(a)-120 _(N) each include one ormore replicated tables (not shown) that correspond to one or more markedtables at primary database 110. When replicated transactions are, forexample, processed successfully by replicate databases 120 _(a)-120_(N), replicated tables in replicate databases 120 _(a)-120 _(N) aresynchronized with corresponding marked tables in primary database 110.

Network 102 can be any type of network or combination of networks suchas, but not limited to, a local area network, wide area network or theInternet. Network 102 can be a form of a wired network or a wirelessnetwork, or a combination thereof. Network 102 can allow primarydatabase 110, replication server 130, replication agent 140, replicatedatabases 120 _(a)-120 _(N) and any other networked components tocommunicate with each other.

Components of system 100 (i.e., replication agent 140, primary database110, replication server 130 and replicate databases 120 _(a)-120 _(N))can be computing devices including one or more processors and mayfurther include one or more modules implemented using one or moreprocessors. Components of system 100 can include any form of physicalstorage such as hard-disk drives, flash drives, random access memory(RAM), and any computer-readable or computer-useable storage media thatmay be configured to store/execute instructions and data. An examplecomputer useful for implementing components of the embodiments isdescribed further below.

Multiple Data-Server Interfaces (DSI)

FIG. 2A illustrates an example system for multi-path replication,according to an embodiment.

Referring to FIG. 2A, embodiments instantiate and maintain a pluralityof replicate connections to replicate database 204. In an embodiment,distributor module (DIST) 202 resolves transactions received fromexecution module (EXEC) 218 (and addressed to replicate database 204)into streams 208 and 210 in accordance with replication subscriptions.FIG. 2A also illustrates data-server interface (DSI) 214 and DSI 216associated with respective streams 208 and 210.

In a non-limiting embodiment, each replicate connection can handle atransaction stream. In a non-limiting embodiment, transactions in thesame stream may conform to the transactions' commit order at primarydatabase 212. Furthermore, in an embodiment transactions in differentstreams (e.g., streams 208 and 210) are applied in parallel and in anorder potentially different from their commit order at primary database212.

EXAMPLE MULTIPLE DSI USER COMMANDS

In a non-limiting embodiment, users may create a default replicateconnection to a replicate database by ‘create connection’ and ‘createconnection . . . using profile’ commands.

As a non-limiting example, in order to create alternate replicateconnections to a replicate database, users may use commands including,but not limited to:

create alternate connection to ds_name. db_name

named conn_server.conn_db

[set error class [to] error_class

set function string class [to] function_class

set username [to] user

set password [to] pwd]

[set param[to] ‘value’]

Example 1

The example commands noted in Example 1 create an alternate (orparallel) replicate connection to a replicate database‘ds_name.db_name’. The name of the alternate replicate connection is‘conn_server.conn_db’.

‘ds_name.db_name’ is the name of the replicate database. As an example,the replicate database may not be a standby database of a warm standbydatabase.

‘conn_server.conn_db’ is used as a name of the alternate replicateconnection.

In a non-limiting embodiment, there may be some constraints on analternate replicate connection name. For example,

a. If ‘conn_server’ is different from ‘ds_name’, an interface entry for‘conn_server’ may exist in the interface file.

b. If ‘conn_server’ is identical to ‘ds_name’, ‘conn_db’ may bedifferent from ‘db_name’.

c. Every replicate connection name can be unique in a replicationsystem.

These examples are purely illustrative and are not intended to limit theembodiments.

Referring to Example 1, users may set ‘[set error class . . . setpassword to pwd]’ configurations for an alternate replicate connection.In a non-limiting embodiment, if ‘set’ clauses are omitted, thealternate replicate connection may inherit these configurations from adefault replicate connection. If there is no default replicateconnection, users may be required to set these configurations.

In an embodiment, these configurations may only be inherited when thereis a route from the controller of the default connection to thecontroller of the alternate connection or when they are controlled bythe same replication server.

In a non-limiting embodiment, if a maintenance user for the alternateconnection is not set, the alternate connection can use the maintenanceuser of the default connection. If a new maintenance user is set, thealternate connection will proceed to use the new maintenance user.

Referring to Example 1, ‘[set param [to] ‘values’]’ connectionconfigurations may be optional. In an embodiment, the specified valuefor these parameters can override an inherited value or a default value.In an embodiment, these configurations may be inherited when the defaultconnection and the alternate connection are controlled by the samereplication server.

Embodiments can support creation of multiple replicate connections to adatabase from multiple replication servers in a common replicationdomain. In an embodiment, each replicate connection may have a uniquename. In a non-limiting embodiment, one replication server may controldefault replicate connections. Other replication servers may controlalternate (or parallel) replicate connections.

In an embodiment, after an alternate replicate connection is created,embodiments can:

-   -   Configure the alternate replicate connection by using ‘alter        connection’ command.    -   Create a subscription using ‘create subscription’ at the        alternate replicate connection.

In an embodiment, an alternate replicate connection can have a row foreach source in table ‘rs_lastcommit’ for duplication detection.

Referring to Example 1, and in an embodiment, ‘drop connection tods_name.db_name’ can support alternate replicate connections.

In an embodiment, ‘ds_name.db_name’ can be a default replicateconnection or an alternate replicate connection.

In an embodiment, when a default connection is dropped, alternateconnections controlled by the default connection's replication servermay also be dropped.

In an embodiment, ‘alter connection to ds_name.db_name’ can supportalternate replicate connections.

In an embodiment ‘ds_name.db_name’ can be a default replicate connectionor an alternate replicate connection.

The following example commands in Example 2 can be used to movesubscriptions between multiple DSI.

alter subscription sub_name

for {table_repdef|func_repdef|{publication pub|

database replication definition db_repdef}

with primary at ds_name.db_name}

move replicate from ds_name.db_name

to ds_name.db_name

Example 2

In an embodiment, the command(s) noted above move transactionssubscribed by a subscription between multiple replicate connections.With this command(s), embodiments can move subscriptions from onereplicate connection to another replicate connection withoutre-materialization.

In an embodiment, the above command(s) can be issued on a replicatereplication server. In an embodiment, to move multiple subscriptions atthe same time, log transfer for primary connections may first besuspended and then resumed after necessary subscriptions are moved.

In a non-limiting embodiment, a subscription may be moved betweenreplicate connections controlled by an identical replication server.

In a non-limiting embodiment, the ‘admin show_connections[, replicate]’command can be used to display a connection name, a replicate database,user and state of all replicate connections.

In an embodiment, ‘rs_databases’ is a database table that can storeconnection information known at a replication server site. With multipleconnections, each connection can have a corresponding row in systemtable ‘rs_databases’. A new column is added to store an ID of aconnection.

In an embodiment, ‘rs_lastcommit’ is a database table storinginformation used by a replication server to find a last transactioncommitted from each data source. In an embodiment, every originaldatabase may have one row in table ‘rs_lastcommit’. In an embodiment,multiple replicate connections apply transactions from an identicaloriginal database in parallel.

In an embodiment, each replicate connection stores a OQID of a lastcommitted transaction in ‘rs_lastcommit’ table. Thus, every replicateconnection can utilize one row in ‘rs_lastcommit’ table. Accordingly,column ‘conn_id’ is added to the ‘rs_lastcommit’ table to identify areplicate connection using a particular row. In an embodiment, areplicate connection uses a row in which ‘conn_id’ equals the replicateconnection's connection id.

In an embodiment, ‘rs_threads’ is a database table storing informationused by a replication server to detect deadlocks and to performtransaction serialization between parallel DSI threads. In anembodiment, replicate connections of multiple DSI threads may need tocheck table entries entered by themselves. Thus, column ‘conn_id’ isadded to identify a replicate connection presently using a row. In anon-limiting embodiment, every replicate connection may use a row inwhich ‘conn_id’ equals the replicate connection's connection id.

In an embodiment, ‘rs_ticket_history’ stores ‘rs_ticket’ information.Embodiments may store store ‘rs_ticket’ information from each replicateconnection. Thus, column ‘conn_id’ is added to identify which replicateconnection is using the row. In a non-limiting embodiment, everyreplicate connection may use a row in which ‘conn_id’ equals thereplicate connection's connection id.

Supporting Multiple Replication Agents

As noted earlier, conventional replication architecture supports asingle path (or stream) of data between a primary (or source) databaseand a replication server. Specifically, in conventional approaches,database transactions are replicated at a target (or replicate)database, serially, in a single replication path to maintain atransaction commit order at the primary database. However, thisreplication architecture is disadvantageous because when throughputactivity at the primary database is high, the replication server, whichreplicates transactions at the target database, cannot maintain a lowreplication latency expected by users at the target database. Thiscauses both data accumulation and significant transaction latency.

In contrast to conventional approaches, embodiments of the inventionenable a replication server to support a plurality of incomingreplication agent connections from a primary database. In an embodiment,to support multiple replication agent threads/connections, thereplication server provides a plurality of primary connections for theprimary database and binds a primary connection with each replicationagent connection.

Referring to FIG. 2B, embodiments instantiate and maintain multiplereplicate connections (e.g., 208 and 210) to replicate database 204. Inan embodiment, DIST modules 220 and 224 resolve transactions forreplicate database 204 into streams 208 and 210 in accordance withreplication subscriptions. FIG. 2B also includes EXEC modules 230 and232 corresponding to respective DIST modules 220 and 224.

In this way, with multiple DSI modules and supporting multiplereplication agent threads through multiple DIST modules, embodiments ofthe invention provide end-to-end multi-path replication.

In an embodiment, a replicate connection for a replicate database and aprimary connection for a primary database can be bound together tocreate an integrated replication path including replication definitionand subscriptions.

In an embodiment, a replicate connection for a standby database and aprimary connection for an active database can be bound together as awarm standby replication path by logical connection.

Multi-Site Availability (MSA) Multi-Path Replication

In a non-limiting embodiment, one or more of the following exampleactions can be performed to setup at least two replication paths betweena primary database and a replicate database. These actions can include,but are not limited to:

-   -   Dividing transactions into at least two sets and ensuring        transactions in the two sets are parallelizable.    -   Creating a default primary connection to the primary database        and creating a default replicate connection to the replicate        database.    -   Creating an alternate primary connection to the primary database        and creating an alternate replicate connection to the replicate        database.    -   Configuring a replication agent to enable at least two senders        and bind transactions to the two senders.    -   Creating a replication definition against a primary database.    -   Creating a subscription against a primary connection and a        replicate connection.

Warm Standby Multi-Path Replication

In a non-limiting embodiment, one or more of the following exampleactions can be performed to setup at least two replication paths betweenan active database and a standby database. These actions include, butare not limited to:

-   -   Dividing transactions into two sets and ensuring transactions in        the two sets are parallelizable.    -   Configuring replication agents at both an active database and a        replicate database to enable at least two replication agent        sender threads, and binding transactions to the at least two        sender threads.    -   Creating a logical connection.    -   Using rs_init to add an active database and a standby database.    -   Creating an alternate logical connection.    -   Creating an alternate active connection for the alternate        logical connection.

Multiple Routes

As a purely illustrative and non-limiting example, consider that thereexist a plurality of primary connections to a primary database in aprimary replication server and a plurality of replicate connections to areplicate database in a replicate replication server. Because theseconnections share a route between the primary replication server and thereplicate replication server, it is possible that the route between theprimary replication server and the replicate replication server becomescongested including multiple replication paths.

To avoid such potential congestion when multiple paths exist,embodiments can instantiate and maintain a plurality of shared routesbetween the primary replication server and the replicate replicationserver.

In addition, embodiments can identify a path with less transactioncongestion compared to transaction congestion in other replication pathsand assign a replication transaction with high replication priority tothe identified path, where the identified path may act as a dedicatedpath for the transaction with high replication priority and any otherhigh priority transactions.

Embodiments instantiate a plurality of replication agent sender threads,where each replication agent sender thread can communicate with adistinct replication server. Embodiments can also associate a set ofdata to a replication agent out-stream or replication path.

In an embodiment, data can be associated to a path based on one or moreparameters/attributes, including, but not limited to:

-   -   Table: Enables association of DML operations performed on a        table to a replication path.    -   Login: Transactions performed by a login name.    -   Server process identifier (SPID)    -   Application name: As a non-limiting example, one or more        transactions performed by an application may be bound to        replication path. In an embodiment, this may require a change in        a begin transaction log record to store application name        information.

In an embodiment, multiple replication streams can also be assigned to areplication server. In a non-limiting embodiment, tables and storedprocedures can be associated (or ‘bound’) to a replication path so thatany replicated data associated with the tables and stored proceduresfollows that path.

Embodiments also enable:

-   -   Binding by login name: In an embodiment, a login name can be        used for binding paths as it is recorded in a begin transaction        log record. While a user ID (UID) can be recorded as well, the        UID may change by the time a replication agent reads the log        record.

Binding by SPID: In an embodiment, all transactions performed by an SPIDcan use an identical replication path.

-   -   Binding by category: In an embodiment, DML operations are        filtered based on content of a column (e.g., “where        state=‘CA’”).

Embodiments also provide support for a plurality of replication agentscanners and a plurality of logical truncation points.

Embodiments enable a replication administrator to define a plurality ofreplicate destinations from a given source database so that replicateddata can be delivered to different and multiple destinations.

Conventionally, as shown in FIG. 3, replication server 302 receives alldata (e.g., data 306 and 308) from source (or primary) database 304.Replication server 302 then conventionally performs data filtering anddelivers filtered data to different destinations, i.e., replicatedatabases 310 and 312. For instance, the replication server 302 deliversdata 306 to replicate database 310 and dat 308 to replicate database312.

In contrast to conventional approaches, and with reference to FIG. 4,embodiments of the invention bind a database object to a channel forreplication and provide the bound object over the channel to areplication server dedicated to said channel.

For example, a channel 430 is controlled by replication server 402 todeliver data to replicate database 406. Also, channel 432 is controlledby replication server 404 to deliver data to replicate database 408. Inthis way, data filtering is accomplished at an early stage, i.e., areplication agent delivers data to a replication server in charge of achannel. Because, a replication server in charge of a channel (or path)may only receive data the replication server needs to deliver to theserver's known destinations, replication transaction load can bedistributed across a plurality of replication servers so that eachreplication server can provide improved replication performance.

Binding Objects to Replication Paths

In an embodiment, when an object is bound to a path or a set of paths,data manipulation language (DML) and data definition language (DDL)operations done on the object will be distributed to path(s) associatedwith the object.

For example, if a table or stored procedure is marked for replication,but has not yet been bound to a path, replication operations may beassigned to a default path.

In an embodiment, the ‘bind’ command creates an association between anamed object and a given replication path.

Parameter Example Usage Action ‘bind’ P1 Object_type - for first releasevalid object types are: table|sproc P2 Object P3 Logical path name P4Unused

In a non-limiting embodiment, parameter “P2, Object” can at least acceptthe following formats:

ownername.objectname, and

objectname

In an embodiment, the “sp_replication_path” stored procedure may supporta pattern matching capability (e.g., wildcards) for names of objects tobe bound (or unbound) to a path.

As a non-limiting example, there can be two characters interchangeablyrecognized as wildcards, i.e., either the percent ‘%’ sign or theasterisk “*” sign may be used to indicate zero or more matchingcharacters.

Example Binding 1: Bind the table object ‘t1’ to the new replicationpath pbd_(—)2

Example Command for Binding 1:

sp_replication_path <dbname>, ‘bind’, “table”, “t1”, “pdb_(—)2”

Example Binding 2: Bind the table object ‘t1’ beloging to ‘owner1’ tothe new replication path pbd_(—)2

Example Command for Binding 2:

sp_replication_path <dbname>, ‘bind’, “table”, “owner1.t1”, “pdb_(—)2”

Example Binding 3: Bind the stored procedure object ‘sproc1’ to the newreplication path pbd_(—)2:

Example Command for Binding 3:

sp_replication_path <dbname>, ‘bind’, “sproc”, “sproc1”, “pdb_(—)2”

Example Binding 4: Bind the dimension table object ‘dt1’ to ‘everywhere’path:

Example Command for Binding 4:

sp_replication_path <dbname>, ‘bind’, “table”, “dt1”, “everywhere”

Example commands to match a table name ‘authors’ to any of the followingwildcard patterns:

sp_replication_path ‘dbname’, ‘bind’, ‘table’, ‘a*’

sp_replication_path ‘dbname’, ‘bind’, ‘table’, ‘au%rs’

sp_replication_path ‘dbname’, ‘bind’, ‘table’, ‘a*th%s’

sp_replication_path ‘dbname’, ‘bind’, ‘table’, ‘authors%’

Embodiments can also enable binding by login or session, e.g.,sp_replication_path <dbname>, ‘bind’, ‘session’

In an embodiment of the present invention, the system and components ofembodiments described herein are implemented using well known computers,such as computer 502 shown in FIG. 5. For example, replication server130, replication agent 150, primary database 110, replicate databases120 a-120N, and any modules (e.g., EXEC, DSI, DIST) can be implementedusing computer(s) 502.

The computer 502 can be any commercially available and well knowncomputer capable of performing the functions described herein, such ascomputers available from International Business Machines, Apple, Sun,HP, Dell, Compaq, Cray, etc.

The computer 502 includes one or more processors (also called centralprocessing units, or CPUs), such as a processor 506. The processor 506is connected to a communication infrastructure 504.

The computer 502 also includes a main or primary memory 508, such asrandom access memory (RAM). The primary memory 508 has stored thereincontrol logic 528A (computer software), and data.

The computer 502 also includes one or more secondary storage devices510. The secondary storage devices 510 include, for example, a hard diskdrive 512 and/or a removable storage device or drive 514, as well asother types of storage devices, such as memory cards and memory sticks.The removable storage drive 514 represents a floppy disk drive, amagnetic tape drive, a compact disk drive, an optical storage device,tape backup, etc.

The removable storage drive 514 interacts with a removable storage unit516. The removable storage unit 516 includes a computer useable orreadable storage medium 524A having stored therein computer software528B (control logic) and/or data. Removable storage unit 516 representsa floppy disk, magnetic tape, compact disk, DVD, optical storage disk,or any other computer data storage device. The removable storage drive514 reads from and/or writes to the removable storage unit 516 in awell-known manner.

The computer 502 also includes input/output/display devices 522, such asmonitors, keyboards, pointing devices, etc.

The computer 502 further includes a communication or network interface518. The network interface 518 enables the computer 502 to communicatewith remote devices. For example, the network interface 518 allows thecomputer 502 to communicate over communication networks or mediums 524B(representing a form of a computer useable or readable medium), such asLANs, WANs, the Internet, etc. The network interface 518 may interfacewith remote sites or networks via wired or wireless connections.

Control logic 528C may be transmitted to and from the computer 502 viathe communication medium 524B.

Any apparatus or manufacture comprising a computer useable or readablemedium having control logic (software) stored therein is referred toherein as a computer program product or program storage device. Thisincludes, but is not limited to, the computer 502, the main memory 508,secondary storage devices 510 and removable storage unit 516. Suchcomputer program products, having control logic stored therein that,when executed by one or more data processing devices cause such dataprocessing devices to operate as described herein, represent embodimentsof the invention.

The invention can work with software, hardware, and/or operating systemimplementations other than those described herein. Any software,hardware, and operating system implementations suitable for performingthe functions described herein can be used.

FIG. 6 is a flowchart that depicts a method 600 of replicating dataaccording to embodiments of the invention. According to the method, anumber of replicate connections are created at step 602. Next,transactions are assigned to the various connections at step 604. Theassignment of transactions can occur a number of different waysaccording to the various embodiments. For instance, according to someembodiments, the transactions are selectively assigned to a replicationpath based on a replication priority. Accordingly to variousembodiments, higher priority transactions might be assigned to a pathhaving less congestion and lower priorities might be assigned to pathshaving more congestion.

At step 606, transactions are applied in parallel to the replicatedatabases in distinct transaction streams. According to someembodiments, the transactions may be applied in an order different fromtheir commit order at the primary database. However, according to someembodiments, transactions applied to the same transaction stream can beapplied in the same order as dictated by their primary database commitorder.

FIG. 7 is a flowchart illustrating a method 700 of replicating dataaccording to embodiments of the present invention. According to themethod, at step 702, a plurality of replication sender threads can becreated. The replication sender threads can communicate in parallel withone or more respective replication servers over one or more replicationpaths. At step 704, data with shared attributes can be grouped accordingto those shared attributes. According to various embodiments sharedattributes may include, for instance, an object type, a table name, anidentifier, a statement category, or a user, to name a few.

At step 708, the method binds data with shared attributes to aparticular replication path that communicates with one of thereplication servers. For instance, data having the same object typemight be bound to the same replication path at this step. At step 708,the data sharing distinct attributes can be replicated over respectivedata paths in parallel.

It is to be appreciated that the Detailed Description section, and notthe Summary and Abstract sections, is intended to be used to interpretthe claims. The Summary and Abstract sections may set forth one or morebut not all exemplary embodiments of the present invention ascontemplated by the inventor(s), and thus, are not intended to limit thepresent invention and the appended claims in any way.

The present invention has been described above with the aid offunctional building blocks illustrating the implementation of specifiedfunctions and relationships thereof. The boundaries of these functionalbuilding blocks have been arbitrarily defined herein for the convenienceof the description. Alternate boundaries can be defined so long as thespecified functions and relationships thereof are appropriatelyperformed.

The foregoing description of the specific embodiments will so fullyreveal the general nature of the invention that others can, by applyingknowledge within the skill of the art, readily modify and/or adapt forvarious applications such specific embodiments, without undueexperimentation, without departing from the general concept of thepresent invention. Therefore, such adaptations and modifications areintended to be within the meaning and range of equivalents of thedisclosed embodiments, based on the teaching and guidance presentedherein. It is to be understood that the phraseology or terminologyherein is for the purpose of description and not of limitation, suchthat the terminology or phraseology of the present specification is tobe interpreted by the skilled artisan in light of the teachings andguidance.

The breadth and scope of the present invention should not be limited byany of the above-described exemplary embodiments, but should be definedonly in accordance with the following claims and their equivalents.

What is claimed is:
 1. A computer-implemented method for databasereplication, comprising: instantiating a plurality of replication senderthreads, said replication sender threads communicating in parallel withrespective replication servers over respective replication paths; andbinding data sharing one or more attributes to a replication path incommunication with said respective replication servers.
 2. The method ofclaim 1, further comprising: binding a database object to a channel forreplication; and providing said bound object over said channel to areplication server dedicated to said channel.
 3. The method of claim 1,further comprising: replicating data sharing a first set of attributesover a first replication path; and replicating data sharing a second setof attributes over a second replication path, wherein said first set ofattributes is distinct from said second set of attributes, and whereinsaid first path and said second path are associated with respectivereplication servers.
 4. The method of claim 1, wherein said attributesinclude one or more of an object type, a table name, an identifier and astatement category.
 5. The method of claim 1, further comprising:defining a plurality of destinations at a source database; anddelivering replicate data, in parallel, to said destinations.
 6. Themethod of claim 1, further comprising: grouping data with sharedattributes according to the shared attributes to create a group.
 7. Themethod of claim 6, wherein binding data sharing one or more attributesto the replication path comprises binding the group to the replicationpath.
 8. The method of claim 1, further comprising: identifying areplication path having less transaction congestion than at least oneother replication path.
 9. The method of claim 8, wherein binding datasharing one or more attributes to a replication comprises binding thedata sharing one or more attributes to the identified replication path.10. The method of claim 1, wherein binding data sharing one or moreattributes to a replication path comprises binding the data according toa replication priority associated with the data.
 11. A system fordatabase replication, comprising: a memory configured to store data; andone or more processors communicatively coupled to the memory, whereinthe processors are configured execute computer instructions stored onthe memory, wherein the computer instructions cause the one or moreprocessors to perform steps comprising: instantiating a plurality ofreplication sender threads, said replication sender threadscommunicating in parallel with respective replication servers overrespective replication paths; and binding data sharing one or moreattributes to a replication path in communication with said respectivereplication servers.
 12. The system of claim 1, wherein the computerinstructions cause the one or more processors to perform steps furthercomprising: binding a database object to a channel for replication; andproviding said bound object over said channel to a replication serverdedicated to said channel.
 13. The system of claim 11, wherein thecomputer instructions cause the one or more processors to perform stepsfurther comprising: replicating data sharing a first set of attributesover a first replication path; and replicating data sharing a second setof attributes over a second replication path, wherein said first set ofattributes is distinct from said second set of attributes, and whereinsaid first path and said second path are associated with respectivereplication servers.
 14. The system of claim 11, wherein the attributesinclude one or more of an object type, a table name, an identifier and astatement category.
 15. The system of claim 11, wherein the computerinstructions cause the one or more processors to perform steps furthercomprising: defining a plurality of destinations at a source database;and delivering replicate data, in parallel, to said destinations. 16.The system of claim 11, wherein the computer instructions cause the oneor more processors to perform steps further comprising: grouping datawith shared attributes according to the shared attributes to create agroup.
 17. The system of claim 16, wherein binding data sharing one ormore attributes to the replication path comprises binding the group tothe replication path.
 18. The system of claim 11, wherein the computerinstructions cause the one or more processors to perform steps furthercomprising: identifying a replication path having less transactioncongestion than at least one other replication path.
 19. The system ofclaim 18, wherein binding data sharing one or more attributes to areplication comprises binding the data sharing one or more attributes tothe identified replication path.
 20. The system of claim 11, whereinbinding data sharing one or more attributes to a replication pathcomprises binding the data according to a replication priorityassociated with the data.